Single Precision Vector Dot Product with &#34;Word&#34; Vector Write Mask

ABSTRACT

The present invention is generally related to the field of image processing, and more specifically to an instruction set for processing images. Vector processing may involve performing a plurality of dot product operations to generate operands for generating operands for a new vector. The dot product operations may require the issue of a plurality of permute instructions to arrange the vector operands in desired locations of a target register. Embodiments of the invention provide a dot product instruction wherein a mask field may be used to specify a particular location of a target register in which to transfer data, thereby avoiding the need for permute instructions for arranging data, reducing dependencies between instructions, and the usage of temporary registers.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to U.S. patent application Ser. No. ______, Attorney Docket No. ROC920060120US1, entitled Single Precision Vector Permute Immediate with “Word” Vector Write Mask, filed Oct. ______, 2006, by Mejdrich et al. This related patent application is herein incorporated by reference in its entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention is generally related to the field of image processing, and more specifically to an instruction set for processing images.

2. Description of the Related Art

The process of rendering two-dimensional images from three-dimensional scenes is commonly referred to as image processing. A particular goal of image rendering is to make two-dimensional simulations or renditions of three-dimensional scenes as realistic as possible. This quest for rendering more realistic scenes has resulted in an increasing complexity of images and innovative methods for processing the complex images.

Two-dimensional images representing a three-dimensional scene are typically displayed on a monitor or some type of display screen. Modern monitors display images through the use of pixels. A pixel is the smallest area of space which can be illuminated on a monitor. Most modern computer monitors use a combination of hundreds of thousands or millions of pixels to compose the entire display or rendered scene. The individual pixels are arranged in a grid pattern and collectively cover the entire viewing area of the monitor. Each individual pixel may be illuminated to render a final picture for viewing.

One method for rendering a real world three-dimensional scene onto a two-dimensional monitor using pixels is called rasterization. Rasterization is the process of taking a two-dimensional image represented in vector format (mathematical representations of geometric objects within a scene) and converting the image into individual pixels for display on the monitor. Rasterization is effective at rendering graphics quickly and using relatively low amounts of computational power; however, rasterization suffers from some drawbacks. For example, rasterization often suffers from a lack of realism because it is not based on the physical properties of light, rather rasterization is based on the shape of three-dimensional geometric objects in a scene projected onto a two dimensional plane. Furthermore, the computational power required to render a scene with rasterization scales directly with an increase in the complexity of objects in the scene to be rendered. As image processing becomes more realistic, rendered scenes become more complex. Therefore, rasterization suffers as image processing evolves, because rasterization scales directly with complexity.

Another method for rendering a real world three-dimensional scene onto a two-dimensional monitor using pixels is called ray tracing. The ray tracing technique traces the propagation of imaginary rays, which behave similar to rays of light, into a three-dimensional scene which is to be rendered onto a computer screen. The rays originate from the eye(s) of a viewer sitting behind the computer screen and traverse through pixels, which make up the computer screen, towards the three-dimensional scene. Each traced ray proceeds into the scene and may intersect with objects within the scene. If a ray intersects an object within the scene, properties of the object and several other contributing factors, for example, the effect of light sources, are used to calculate the amount of color and light, or lack thereof, the ray is exposed to. These calculations are then used to determine the final color of the pixel through which the traced ray passed.

The process of tracing rays is carried out many times for a single scene. For example, a single ray may be traced for each pixel in the display. Once a sufficient number of rays have been traced to determine the color of all of the pixels which make up the two-dimensional display of the computer screen, the two dimensional synthesis of the three-dimensional scene can be displayed on the computer screen to the viewer.

Ray tracing typically renders real world three dimensional scenes with more realism than rasterization. This is partially due to the fact that ray tracing simulates how light travels and behaves in a real world environment, rather than simply projecting a three dimensional shape onto a two dimensional plane as is done with rasterization. Therefore, graphics rendered using ray tracing more accurately depict on a monitor what our eyes are accustomed to seeing in the real world.

Furthermore, ray tracing also handles increasing scene complexity better than rasterization. Ray tracing scales logarithmically with scene complexity. This is due to the fact that the same number of rays may be cast into a scene, even if the scene becomes more complex. Therefore, ray tracing does not suffer in terms of computational power requirements as scenes become more complex unlike rasterization.

However, one major drawback of ray tracing is the large number of floating point calculations, and thus increased processing power, required to render scenes. This leads to problems when fast rendering is needed, for example, when an image processing system is to render graphics for animation purposes such as in a game console. Due to the increased computational requirements for ray tracing it is difficult to render animation quickly enough to seem realistic (realistic animation is approximately twenty to twenty-four frames per second).

Image processing using, for example, ray tracing, may involve performing both vector and scalar math. Accordingly, hardware support for image processing may include vector and scalar units configured to perform a wide variety of calculations. The vector and scalar operations, for example, may trace the path of light through a scene, or move objects within a three-dimensional scene. A vector unit may perform operations, for example, dot products and cross products, on vectors related to the objects in the scene. A scalar unit may perform arithmetic operations on scalar values, for example, addition, subtraction, multiplication, division, and the like.

The vector and scalar units may be pipelined to improve performance. However, performing vector operations may involve performing multiple iterations of multiple instructions which may be dependent on each other. Such dependencies between instructions may reduce the efficiency of the pipelined units. For example, several pipeline stages may be left unused in order for a first instruction to complete prior to execution of a second instruction.

Furthermore, each vector unit may be coupled with a register file comprising the vector data processed by the vector unit. The vector data may be contained in one or more locations in one or more registers. Therefore, one or more instructions may be issued to rearrange the vector data in desired locations within a target register. The multiple instructions rearranging vector data may limit the efficiency of vector processing by consuming a significant portion of the issue bandwidth. Additionally, the one or more instructions rearranging vector data may be dependent on one another, thereby introducing further pipeline stalls and unused pipeline stages that further limit efficiency.

Moreover, rearranging vector data may require the use of multiple temporary registers. The use of large numbers of temporary registers introduces yet another inefficiency because it requires the construction of large register files that consume valuable space and limit processing of vector data based on the availability of registers.

Therefore, what is needed are more efficient methods, systems, and articles of manufacture for processing vector data.

SUMMARY OF THE INVENTION

The present invention is generally related to the field of image processing, and more specifically to an instruction set for processing images.

One embodiment of the invention provides a method for storing data in a target register. The method generally comprises receiving a dot product instruction specifying at least one source register comprising vector operands for performing a dot product operation, the target register, and a write mask. The write mask identifies one or more locations of the target register for writing data. The method further comprises, in response to receiving the dot product instruction, performing the dot product operation and storing a scalar result of the dot product operation to the one or more locations of the target register identified by the write mask.

Another embodiment of the invention provides a method for constructing a vector in a target register. The method generally comprises generating a plurality of dot product instructions, each dot product instruction specifying at least one source register comprising vector operands for performing a dot product operation, and the target register, wherein each dot product instruction generates a scalar result representing an operand of the vector. The method further comprises setting a mask field in each of the plurality of dot product instructions, wherein the mask field identifies one or more locations of the target register for storing the scalar result of the dot product operation, and executing the dot product instructions to store each operand of the vector at the one or more locations in the target register identified by the mask field to construct the vector in the target register.

Yet another embodiment of the invention provides a system, comprising a plurality of processors communicably coupled with one another. Each processor generally comprises a register file comprising a plurality of registers and at least one vector unit. The vector unit is generally configured to receive a dot product instruction specifying at least one source register comprising vector operands for performing a dot product operation, a target register, and a write mask, the write mask identifying one or more locations in the target register, and execute the dot product instruction by performing the dot product operation and storing a scalar result of the dot product operation to the one or more locations of the target register identified by the write mask.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above recited features, advantages and objects of the present invention are attained and can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to the embodiments thereof which are illustrated in the appended drawings.

It is to be noted, however, that the appended drawings illustrate only typical embodiments of this invention and are therefore not to be considered limiting of its scope, for the invention may admit to other equally effective embodiments.

FIG. 1 illustrates a multiple core processing element, according to one embodiment of the invention.

FIG. 2 illustrates a multiple core processing element network, according to an embodiment of the invention.

FIG. 3 is an exemplary three dimensional scene to be rendered by an image processing system, according to one embodiment of the invention.

FIG. 4 illustrates a detailed view of an object to be rendered on a screen, according to an embodiment of the invention.

FIG. 5 illustrates a cross product operation.

FIG. 6 illustrates a register according to an embodiment of the invention.

FIG. 7 illustrates a vector unit and a register file, according to an embodiment of the invention.

FIG. 8 illustrates a detailed view of a vector unit according to an embodiment of the invention.

FIG. 9A illustrates an exemplary registers according to an embodiment of the invention.

FIG. 9B illustrates an exemplary register file according to an embodiment of the invention.

FIG. 10 illustrates an exemplary instruction stream for constructing a vector, according to an embodiment of the invention.

FIG. 11 illustrates an exemplary dot product instruction according to an embodiment of the invention.

FIG. 12 illustrates another exemplary instruction stream according to an embodiment of the invention.

FIG. 13 is a flow diagram of exemplary operations performed to construct a new vector in a target register, according to an embodiment of the invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present invention is generally related to the field of image processing, and more specifically to an instruction set for processing images. Vector processing may involve performing a plurality of dot product operations to generate operands for generating operands for a new vector. The dot product operations may require the issue of a plurality of permute instructions to arrange the vector operands in desired locations of a target register. Embodiments of the invention provide a dot product instruction wherein a mask field may be used to specify a particular location of a target register in which to transfer data, thereby avoiding the need for permute instructions for arranging data, reducing dependencies between instructions, and the usage of temporary registers.

In the following, reference is made to embodiments of the invention. However, it should be understood that the invention is not limited to specific described embodiments. Instead, any combination of the following features and elements, whether related to different embodiments or not, is contemplated to implement and practice the invention. Furthermore, in various embodiments the invention provides numerous advantages over the prior art. However, although embodiments of the invention may achieve advantages over other possible solutions and/or over the prior art, whether or not a particular advantage is achieved by a given embodiment is not limiting of the invention. Thus, the following aspects, features, embodiments and advantages are merely illustrative and are not considered elements or limitations of the appended claims except where explicitly recited in a claim(s). Likewise, reference to “the invention” shall not be construed as a generalization of any inventive subject matter disclosed herein and shall not be considered to be an element or limitation of the appended claims except where explicitly recited in a claim(s).

An Exemplary Processor Layout and Communications Network

FIG. 1 illustrates an exemplary multiple core processing element 100, in which embodiments of the invention may be implemented. The multiple core processing element 100 includes a plurality of basic throughput engines 105 (BTEs). A BTE 105 may contain a plurality of processing threads and a core cache (e.g., an L1 cache). The processing threads located within each BTE may have access to a shared multiple core processing element cache 110 (e.g., an L2 cache).

The BTEs 105 may also have access to a plurality of inboxes 115. The inboxes 115 may be a memory mapped address space. The inboxes 115 may be mapped to the processing threads located within each of the BTEs 105. Each thread located within the BTEs may have a memory mapped inbox and access to all of the other memory mapped inboxes 115. The inboxes 115 make up a low latency and high bandwidth communications network used by the BTEs 105.

The BTEs may use the inboxes 115 as a network to communicate with each other and redistribute data processing work amongst the BTEs. For some embodiments, separate outboxes may be used in the communications network, for example, to receive the results of processing by BTEs 105. For other embodiments, inboxes 115 may also serve as outboxes, for example, with one BTE 105 writing the results of a processing function directly to the inbox of another BTE 105 that will use the results.

The aggregate performance of an image processing system may be tied to how well the BTEs can partition and redistribute work. The network of inboxes 115 may be used to collect and distribute work to other BTEs without corrupting the shared multiple core processing element cache 110 with BTE communication data packets that have no frame to frame coherency. An image processing system which can render many millions of triangles per frame may include many BTEs 105 connected in this manner.

In one embodiment of the invention, the threads of one BTE 105 may be assigned to a workload manager. An image processing system may use various software and hardware components to render a two dimensional image from a three dimensional scene. According to one embodiment of the invention, an image processing system may use a workload manager to traverse a spatial index with a ray issued by the image processing system. A spatial index may be implemented as a tree type data structure used to partition a relatively large three dimensional scene into smaller bounding volumes. An image processing system using a ray tracing methodology for image processing may use a spatial index to quickly determine ray-bounding volume intersections. In one embodiment of the invention, the workload manager may perform ray-bounding volume intersection tests by using the spatial index.

In one embodiment of the invention, other threads of the multiple core processing element BTEs 105 on the multiple core processing element 100 may be vector throughput engines. After a workload manager determines a ray-bounding volume intersection, the workload manager may issue (send), via the inboxes 115, the ray to one of a plurality of vector throughput engines. The vector throughput engines may then determine if the ray intersects a primitive contained within the bounding volume. The vector throughput engines may also perform operations relating to determining the color of the pixel through which the ray passed.

FIG. 2 illustrates a network of multiple core processing elements 200, according to one embodiment of the invention. FIG. 2 also illustrates one embodiment of the invention where the threads of one of the BTEs of the multiple core processing element 100 is a workload manager 205. Each multiple core processing element 220 _(1-N) in the network of multiple core processing elements 200 may contain one workload manager 205 _(1-N), according to one embodiment of the invention. Each processor 220 in the network of multiple core processing elements 200 may also contain a plurality of vector throughput engines 210, according to one embodiment of the invention.

The workload managers 220 _(1-N) may use a high speed bus 225 to communicate with other workload managers 220 _(1-N) and/or vector throughput engines 210 of other multiple core processing elements 220, according to one embodiment of the invention. Each of the vector throughput engines 210 may use the high speed bus 225 to communicate with other vector throughput engines 210 or the workload managers 205. The workload manager processors 205 may use the high speed bus 225 to collect and distribute image processing related tasks to other workload manager processors 205, and/or distribute tasks to other vector throughput engines 210. The use of a high speed bus 225 may allow the workload managers 205 _(1-N) to communicate without affecting the caches 230 with data packets related to workload manager 205 communications.

An Exemplary Three Dimensional Scene

FIG. 3 is an exemplary three dimensional scene 305 to be rendered by an image processing system. Within the three dimensional scene 305 may be objects 320. The objects 320 in FIG. 3 are of different geometric shapes. Although only four objects 320 are illustrated in FIG. 3, the number of objects in a typical three dimensional scene may be more or less. Commonly, three dimensional scenes will have many more objects than illustrated in FIG. 3.

As can be seen in FIG. 3 the objects are of varying geometric shape and size. For example, one object in FIG. 3 is a pyramid 320 _(A). Other objects in FIG. 3 are boxes 320 _(B-D). In many modern image processing systems objects are often broken up into smaller geometric shapes (e.g., squares, circles, triangles, etc.). The larger objects are then represented by a number of the smaller simple geometric shapes. These smaller geometric shapes are often referred to as primitives.

Also illustrated in the scene 305 are light sources 325 _(A-B). The light sources may illuminate the objects 320 located within the scene 305. Furthermore, depending on the location of the light sources 325 and the objects 320 within the scene 305, the light sources may cause shadows to be cast onto objects within the scene 305.

The three dimensional scene 305 may be rendered into a two-dimensional picture by an image processing system. The image processing system may also cause the two-dimensional picture to be displayed on a monitor 310. The monitor 310 may use many pixels 330 of different colors to render the final two-dimensional picture.

One method used by image processing systems to render a three-dimensional scene 320 into a two dimensional picture is called ray tracing. Ray tracing is accomplished by the image processing system “issuing” or “shooting” rays from the perspective of a viewer 315 into the three-dimensional scene 320. The rays have properties and behavior similar to light rays.

One ray 340, that originates at the position of the viewer 315 and traverses through the three-dimensional scene 305, can be seen in FIG. 3. As the ray 340 traverses from the viewer 315 to the three-dimensional scene 305, the ray 340 passes through a plane where the final two-dimensional picture will be rendered by the image processing system. In FIG. 3 this plane is represented by the monitor 310. The point the ray 340 passes through the plane, or monitor 310, is represented by a pixel 335.

As briefly discussed earlier, most image processing systems use a grid 330 of thousands (if not millions) of pixels to render the final scene on the monitor 310. Each individual pixel may display a different color to render the final composite two-dimensional picture on the monitor 310. An image processing system using a ray tracing image processing methodology to render a two dimensional picture from a three-dimensional scene will calculate the colors that the issued ray or rays encounters in the three dimensional scene. The image processing scene will then assign the colors encountered by the ray to the pixel through which the ray passed on its way from the viewer to the three-dimensional scene.

The number of rays issued per pixel may vary. Some pixels may have many rays issued for a particular scene to be rendered. In which case the final color of the pixel is determined by the each color contribution from all of the rays that were issued for the pixel. Other pixels may only have a single ray issued to determine the resulting color of the pixel in the two-dimensional picture. Some pixels may not have any rays issued by the image processing system, in which case their color may be determined, approximated or assigned by algorithms within the image processing system.

To determine the final color of the pixel 335 in the two dimensional picture, the image processing system must determine if the ray 340 intersects an object within the scene. If the ray does not intersect an object within the scene it may be assigned a default background color (e.g., blue or black, representing the day or night sky). Conversely, as the ray 340 traverses through the three dimensional scene the ray 340 may strike objects. As the rays strike objects within the scene the color of the object may be assigned the pixel through which the ray passes. However, the color of the object must be determined before it is assigned to the pixel.

Many factors may contribute to the color of the object struck by the original ray 340. For example, light sources within the three dimensional scene may illuminate the object. Furthermore, physical properties of the object may contribute to the color of the object. For example, if the object is reflective or transparent, other non-light source objects may then contribute to the color of the object.

In order to determine the effects from other objects within the three dimensional scene, secondary rays may be issued from the point where the original ray 340 intersected the object. For example, one type of secondary ray may be a shadow ray. A shadow ray may be used to determine the contribution of light to the point where the original ray 340 intersected the object. Another type of secondary ray may be a transmitted ray. A transmitted ray may be used to determine what color or light may be transmitted through the body of the object. Furthermore, a third type of secondary ray may be a reflected ray. A reflected ray may be used to determine what color or light is reflected onto the object.

As noted above, one type of secondary ray may be a shadow ray. Each shadow ray may be traced from the point of intersection of the original ray and the object, to a light source within the three-dimensional scene 305. If the ray reaches the light source without encountering another object before the ray reaches the light source, then the light source will illuminate the object struck by the original ray at the point where the original ray struck the object.

For example, shadow ray 341 _(A) may be issued from the point where original ray 340 intersected the object 320 _(A), and may traverse in a direction towards the light source 325 _(A). The shadow ray 341 _(A) reaches the light source 325 _(A) without encountering any other objects 320 within the scene 305. Therefore, the light source 325 _(A) will illuminate the object 320 _(A) at the point where the original ray 340 intersected the object 320 _(A).

Other shadow rays may have their path between the point where the original ray struck the object and the light source blocked by another object within the three-dimensional scene. If the object obstructing the path between the point on the object the original ray struck and the light source is opaque, then the light source will not illuminate the object at the point where the original ray struck the object. Thus, the light source may not contribute to the color of the original ray and consequently neither to the color of the pixel to be rendered in the two-dimensional picture. However, if the object is translucent or transparent, then the light source may illuminate the object at the point where the original ray struck the object.

For example, shadow ray 341 _(B) may be issued from the point where the original ray 340 intersected with the object 320 _(A), and may traverse in a direction towards the light source 325 _(B). In this example, the path of the shadow ray 341 _(B) is blocked by an object 320 _(D). If the object 320 _(D) is opaque, then the light source 325 _(B) will not illuminate the object 320 _(A) at the point where the original ray 340 intersected the object 320 _(A). However, if the object 320 _(D) which the shadow ray is translucent or transparent the light source 325 _(B) may illuminate the object 320 _(A) at the point where the original ray 340 intersected the object 320 _(A).

Another type of secondary ray is a transmitted ray. A transmitted ray may be issued by the image processing system if the object with which the original ray intersected has transparent or translucent properties (e.g., glass). A transmitted ray traverses through the object at an angle relative to the angle at which the original ray struck the object. For example, transmitted ray 344 is seen traversing through the object 320 _(A) which the original ray 340 intersected.

Another type of secondary ray is a reflected ray. If the object with which the original ray intersected has reflective properties (e.g. a metal finish), then a reflected ray will be issued by the image processing system to determine what color or light may be reflected by the object. Reflected rays traverse away from the object at an angle relative to the angle at which the original ray intersected the object. For example, reflected ray 343 may be issued by the image processing system to determine what color or light may be reflected by the object 320 _(A) which the original ray 340 intersected.

The total contribution of color and light of all secondary rays (e.g., shadow rays, transmitted rays, reflected rays, etc.) will result in the final color of the pixel through which the original ray passed.

Vector Operations

Processing images may involve performing one or more vector operations to determine, for example, intersection of rays and objects, generation of shadow rays, reflected rays, and the like. One common operation performed during image processing is the cross product operation between two vectors. A cross product may be performed to determine a normal vector from a surface, for example, the surface of a primitive of an object in a three dimensional scene. The normal vector may indicate whether the surface of the object is visible to a viewer.

As previously described, each object in a scene may be represented as a plurality of primitives connected to one another to form the shape of the object. For example, in one embodiment, each object may be composed of a plurality of interconnected triangles. FIG. 4 illustrates an exemplary object 400 composed of a plurality of triangles 410. Object 400 may be a spherical object, formed by the plurality of triangles 410 in FIG. 4. For purposes of illustration a crude spherical object is shown. One skilled in the art will recognize that the surface of object 400 may be formed with a greater number of smaller triangles 410 to better approximate a curved object.

In one embodiment of the invention, the surface normal for each triangle 410 may be calculated to determine whether the surface of the triangle is visible to a viewer 450. To determine the surface normal for each triangle, a cross product operation may be performed between two vectors representing two sides of the triangle. For example, the surface normal 413 for triangle 410 a may be computed by performing a cross product between vectors 411 a and 411 b.

The normal vector may determine whether a surface, for example, the surface of a primitive, faces a viewer. Referring to FIG. 4, normal vector 413 points in the direction of viewer 450. Therefore, triangle 410 may be displayed to the user. On the other hand, normal vector 415 of triangle 410 b points away from viewer 450. Therefore, triangle 410 b may not be displayed to the viewer.

FIG. 5 illustrates a cross product operation between two vectors A and B. As illustrated, vector A may be represented by coordinates [x_(a), y_(a), z_(a)], and vector B may be represented by coordinates [x_(b), y_(b), z_(b)]. The cross product A X B results in a vector N that is perpendicular (normal) to a plane comprising vectors A and B. The coordinates of the normal vector, as illustrated are [(y_(a)z_(b)−y_(b)z_(a)), (x_(b)z_(a)−x_(a)z_(b)), (x_(a)y_(b)−x_(b)y_(a))]. One skilled in the art will recognize that vector A may correspond to vector 411 a in FIG. 4, vector B may correspond to vector 411 b, and vector N may correspond to normal vector 413.

Another common vector operation performed during image processing is the dot product operation. A dot product operation may be performed to determine rotation, movement, positioning of objects in the scene, and the like. A dot product operation produces a scalar value that is independent of the coordinate system and represents an inner product of the Euclidean space. The equation below describes a dot product operation performed between the previously described vectors A and B:

A·B=x _(a) ·x _(b) +y _(a) ·y _(b) +z _(a) ·z _(b)

Hardware Support for Performing Vector Operations

As described earlier, a vector throughput engine (VTE), for example VTE 210 in FIG. 2, may perform operations to determine whether a ray intersects with a primitive, and determine a color of a pixel through which a ray is passed. The operations performed may include a plurality of vector and scalar operations. Accordingly, VTE 210 may be configured to issue instructions to a vector unit for performing vector operations.

Vector processing may involve issuing one or more vector instructions. The vector instructions may be configured to perform operations involving one or more operands in one or more registers. The one or more registers may be a part of a register file associated with a vector unit. FIG. 6 illustrates an exemplary register 600 comprising one or more operands. As illustrated in FIG. 6, each register in the register file may comprise a plurality of sections, wherein each section comprises an operand.

In the embodiment illustrated in FIG. 6, register 600 is shown as a 128 bit register. Register 600 may be divided into four 32 bit word sections: word 0, word 1, word 2, and word 3, as illustrated. Word 0 may include bits 0-31, word 1 may include bits 32-63, word 2 may include bits 64-97, and word 3 may include bits 98-127, as illustrated. However, one skilled in the art will recognize that register 600 may be of any reasonable length and may include any number of sections of any reasonable length.

Each section in register 600 may include an operand for a vector operation. For example, register 600 may include the coordinates and data for a vector, for example vector A of FIG. 5. Accordingly, word 0 may include coordinate x_(a), word 1 may include the coordinate y_(a), and word 2 may include the coordinate z_(a). Word 3 may include data related to a primitive associated with the vector, for example, color, transparency, and the like. In one embodiment, word 3 may be used to store scalar values. The scalar values may or may not be related to the vector coordinates contained in words 0-2.

FIG. 7 illustrates an exemplary vector unit 700 and an associated register file 710. Vector unit 700 may be configured to execute single instruction multiple data (SIMD) instructions. In other words, vector unit 700 may operate on one or more vectors to produce a single scalar or vector result. For example, vector unit 700 may perform parallel operations on data elements that comprise one or more vectors to produce a scalar or vector result.

A plurality of vectors operated on by the vector unit may be stored in register file 710. For example, in FIG. 7, register file 710 provides 32 128-bit registers 711 (R0-R31). Each of the registers 711 may be organized in a manner similar to register 600 of FIG. 6. Accordingly, each register 711 may include vector data, for example, vector coordinates, pixel data, transparency, and the like. Data may be exchanged between register file 710 and memory, for example, cache memory, using load and store instructions. Accordingly, register file 710 may be communicably coupled with a memory device, for example, a Dynamic Random Access memory (DRAM) device and/or a cache (SRAM) device

A plurality of lanes 720 may connect register file 710 to vector unit 700. Each lane may be configured to provide input from a register file to the vector unit. For example, in FIG. 7, three 128 bit lanes connect the register file to the vector unit 700. In this manner, the contents of any 3 registers from register file 710 may be provided to the vector unit at a time.

The results of an operation performed by the vector unit may be written back to register file 710. For example, a 128 bit lane 721 provides a write back path to write results computed by vector unit 700 back to any one of the registers 711 of register file 710.

FIG. 8 illustrates a detailed view of a vector unit 800. Vector unit 800 is an embodiment of the vector unit 700 depicted in FIG. 7. As illustrated in FIG. 8, vector unit 800 may include a plurality of processing lanes. For example, three processing lanes 810, 820, and 830 are shown in FIG. 8. Each processing lane may be configured to perform an operation in parallel with one or more other processing lanes. For example, each processing lane may multiply a pair of operands to perform a cross product or dot product operation. By multiplying different pairs of operands in different processing lanes of the vector unit, vector operations may be performed faster and more efficiently.

In one embodiment of the invention, one or more processing lanes of vector unit 800 may be configured to perform scalar operations. Therefore, vector unit 800 may be configured to perform both scalar and vector operations. For example, in one embodiment, vector unit 800 may include four processing lanes, wherein three processing lanes are configured to perform vector operations and one processing lane is configured to perform scalar operations.

Each processing lane may be pipelined to further improve performance. Accordingly, each processing lane may include a plurality of pipeline stages, with each stage performing one or more operations on the operands. For example, each vector lane may include a multiplier 851 for multiplying a pair of operands 830 and 831. Operands 830 and 831 may be derived from one of the lanes coupling the register file with the vector unit, for example, lanes 720 in FIG. 7. In one embodiment of the invention, the multiplication of operands may be performed in a first stage of the pipeline as illustrated in FIG. 8.

Each processing lane may also include an aligner for aligning the product computed by multiplier 851. For example, an aligner 852 may be provided in each processing lane. Aligner 852 may be configured to adjust a decimal point of the product computed by a multiplier 851 to a desirable location in the result. For example, aligner 852 may be configured to shift the bits of the product computed multiplier 851 by one or more locations, thereby putting the product in desired format. While alignment is shown as a separate pipeline stage in FIG. 8, one skilled in the art will recognize that the multiplication and alignment may be performed in the same pipeline stage.

Each processing lane may also include an adder 853 for adding two or more operands. In one embodiment (illustrated in FIG. 8), each adder 853 is configured to receive the product computed by a multiplier, and add the product to another operand 832. Operand 832, like operands 830 and 831, may be derived from one of the lanes connecting the register file to the vector unit. Therefore, each processing lane may be configured to perform a multiply-add instruction. One skilled in the art will recognize that multiply-add instructions are frequently performed in vector operations. Therefore, by performing several multiply add instructions in parallel lanes, the efficiency of vector processing may be significantly improved.

Each vector processing lane may also include a normalizing stage and a rounding stage, as illustrated in FIG. 8. Accordingly, a normalizer 854 may be provided in each processing lane. Normalizer 854 may be configured to represent a computed value in a convenient exponential format. For example, normalizer may receive the value 0.0000063 as a result of an operation. Normalizer 854 may convert the value into a more suitable exponential format, for example, 6.3×10⁻⁶. The rounding stage may involve rounding a computed value to a desired number of decimal points. For example, a computed value of 10.5682349 may be rounded to 10.568 if only three decimal places are desired in the result. In one embodiment of the invention the rounder may round the least significant bits of the particular precision floating point number the rounder is designed to work with.

One skilled in the art will recognize that embodiments of the invention are not limited to the particular pipeline stages, components, and arrangement of components described above and in FIG. 8. For example, in some embodiments, aligner 852 may be configured to align operand 832, a product computed by the multiplier, or both. Furthermore, embodiments of the invention are not limited to the particular components described in FIG. 8. Any combination of the illustrated components and additional components such as, but not limited to, leading zero adders, dividers, etc. may be included in each processing lane.

In one embodiment of the invention, one or more vector units may be coupled with a register file. For example, in one embodiment, two vector units may be coupled with the register file. Each vector unit may be configured to independently and simultaneously process vector and scalar instructions. In one embodiment, one or more resources in a first vector unit may be shared with a second vector unit to process an instruction, for example, a cross product instruction.

Constructing a Vector by Performing Dot Product Operations

Vector processing often involves performing a plurality of dot product operations. The scalar results of each dot product operation may be used to create new vectors. For example, a first dot product operations may generate a first operand of a vector, a second dot product operation may generate a second operand of the vector, and a third dot product operation may generate a third operand of the vector. Therefore, a vector may be constructed by performing a plurality of dot product operations.

As previously described, executing a vector instruction, such as a dot product instruction may involve performing a plurality of operations on one or more vector elements in one or more processing lanes of the vector unit. For example, each lane of the vector unit may perform an operation on one or more vector elements. The vector elements on which the operation is performed may depend on the location of the elements in one or more registers specified by the instruction. Therefore, vector elements may be arranged in appropriate locations in source registers prior to executing an instruction.

FIG. 9A illustrates exemplary source registers R_(A) and R_(B), comprising the vector elements for two vectors A and B, for example vectors A and B of FIG. 5. As illustrated in FIG. 9A, register R_(A) may comprise vector operand x_(a) in its word 0 location, operand y_(a) in its word 1 location, and operand z_(a) in its word 2 location. Similarly, register R_(B) may comprise vector operand x_(b) in its word 0 location, operand y_(b) in its word 1 location, and operand z_(b) in its word 2 location. The data in the word 3 location of register R_(A) and R_(B) is shown as “don't-care” data, and is therefore depicted as XX.

Vector processing may involve performing a wide variety of operations, for example, cross products, dot products, vector addition, and the like. For example, in one embodiment a dot product operation may be performed between vectors A and B. Accordingly, a dot product instruction identifying registers R_(A) and R_(B) may be issued to a vector unit. The vector unit may be configured to multiply elements of vectors A and B contained in registers R_(A) and R_(B). For example, referring back to FIG. 7, the contents of registers R_(A) and R_(B) may be transferred to the vector unit via lanes 720 to one or more processing lanes of the vector unit.

A first processing lane of the vector unit may multiply vector elements in the word 0 locations of register R_(A) and R_(B), a second processing lane may multiply vector elements in the word 1 locations of R_(A) and R_(B), and a third processing lane may multiply vector elements in the word 2 locations of R_(A) and R_(B). The products may then be added in a final pipeline stage of the vector unit to determine the scalar dot product.

The result of the dot product instruction may be stored in register R_(C), shown in FIG. 9A. For example, referring back to FIG. 7, the results of the dot product instruction may be written back to register R_(C) in register file 710 via lane 721. As illustrated, the scalar result may be stored across all the register locations of register R_(C), as shown in FIG. 9A.

One problem with constructing vectors using dot products is that each scalar dot product result is spread out across an entire register (commonly referred to as ‘splatted’). Therefore, each vector element may be stored in a different register. This requires further operations to combine the multiple scalar results in different registers to form a vector, in a single register, like, for example, Registers R_(A) and R_(B).

FIG. 9B illustrates vector elements of vectors A and B spread across various locations and in various registers of a register file 900. For example, element x_(a) is contained in register R7, element y_(a) is contained in register R3, and element z_(a) is contained in register R1. Elements x_(a), y_(a) and z_(a) may have been stored in registers R7, R3, and R1 respectively as a result of dot product operations performed to generate the elements. The elements of vector A may require arrangement into a single register, as shown, for example, in register R_(A) of FIG. 9A, wherein x_(a) is contained in the word 0 location, y_(a) is contained in the word 1 location and z_(a) is contained in the word 2 location. This may be done to perform further vector operations using vector A in register R_(A).

A variety of permute instructions may be issued to rearrange and transfer vector elements in a plurality of registers to achieve a desired configuration of the vector elements in one or more registers. FIG. 10 illustrates an exemplary instruction stream to construct a new vector by performing a plurality of dot product instructions and a plurality of permute instructions to arrange the elements of vector A, shown in FIG. 9B, in appropriate locations of a single register R_(A).

As illustrated in FIG. 10, a first dot product instruction 1001 may be issued to generate a first vector operand x_(a) for register A. The dot product instruction may identify two source registers which contain the operands for performing dot product operation. For example, two source registers R10 and R20 are identified in instruction 1001. The dot product instruction may also identify a target register for temporarily storing the scalar result of the dot product operation. For example, register R7 is identified as the target register for storing the results of instruction 1001. As a result of executing instruction 1001, the scalar result of the dot product, x_(a), may be stored in register R7, as shown in FIG. 9B. Similarly, dot product instructions 1002 and 1003 may be performed to store operand y_(a) of vector A in register R3 and operand z_(a) of vector A in register R1, as illustrated in FIG. 10.

Because the operands of vector A are stored in different registers, the operands may be transferred into desired locations of a single register that may represent vector A (for example, register R_(A) in FIG. 9A). A plurality of permute instructions may be issued to transfer vector A operands into desired locations of a desired register. As illustrated in FIG. 10, a first permute instruction 1004 may move z_(a) from register R1 into a temporary register T1. Similarly, instruction 1005 may move y_(a) from register R3 into a temporary register T2, and instruction 1006 may move x_(a) from register R7 into a temporary register T3.

Subsequently, a merge instruction 1007 may be issued to merge the contents of registers T2 and T3, and store the merged contents in register R_(A). As a result of the merge instruction, register R_(A) may contain x_(a) in its word 0 location and y_(a) in its word 1 location. A second merge instruction 1008 may be issued to merge the contents of registers R_(A) and T1. The second merge instruction may transfer z_(a) into the word 2 location of R_(A). Therefore, the elements of vector A may be arranged in register R_(A) as shown in FIG. 9A. Similar instructions may be issued to arrange elements of vector B in register R_(B) as shown in FIG. 9A prior to performing the dot product operation between registers R_(A) and R_(B).

As previously discussed, execution of instructions, for example, instructions 1004-1008 may be pipelined to improve performance. However, dependencies between the instructions may require pipeline stalls. For example, instruction 1007 may be dependent on instructions 1005 and 1006. The dependency may exist because the transfer of elements x_(a) and y_(a) into appropriate locations in registers T2 and T3 must be completed before the contents of registers T2 and T3 can be merged. Therefore, one or more pipeline stages may be stalled to allow completion of instructions 1005 and 1006 before execution of instruction 1007 begins.

Similarly, instruction 1008 may be dependant on instruction 1007. This dependency may exist because both instructions 1007 and 1008 access the same register R_(A). Therefore, operation on register R_(A) by instruction 1007 may be allowed to complete before operations on register R_(A) by instruction 1008 begin. Accordingly, the pipeline may be stalled between instructions 1007 and 1008.

Dot Product Instruction with Write Mask

In one embodiment of the invention, dot instructions may include, as an operand, a write mask to identify a particular location of a desired register in which to write the scalar result of the dot product. Therefore, the issue of permute instructions and the use of temporary registers to store vector elements may be avoided.

FIG. 11 illustrates an exemplary dot product instruction with a write mask according to an embodiment of the invention. As illustrated, the instruction may include an op-code field 1101, one or more source register fields (two source register fields 1102 and 1103 are shown), a target register field 1104 and a mask field 1105. The register fields may comprise any suitable number of bits to specify source and target registers, and the exact number of bits may depend on the number of registers in a particular system architecture. For example, 5-bit register fields may be used to specify one of 32 source and target registers, while 7-bit register fields may be used to specify one of 128 source and target registers.

Mask field 1105 may specify one or more locations within the target register identified in field 1104 in which data may be stored. For example, in one embodiment, mask field 1105 may identify a word location, for example, word 0, word 1, word 2, word 3, and the like, where the results may be stored. In one embodiment, mask field 1105 may include a single bit for each identifiable field in the target register. For example, in one embodiment, the mask field may include four bits to identify four word locations. For example, a first bit may be associated with word location 0, a second bit with word location 1, a third bit with word location 2, and a fourth bit with word location 3.

Accordingly, if a mask bit is enabled, the data may be written to the word location associated with the bit. For example, in one embodiment, the mask may be set to 0001, wherein logic ‘0’ may denote a disabled bit and logic ‘1’ may denote an enabled bit. Because the fourth logic bit is enabled, results may be written to word 3 of the target register. If, instead, the mask bit was set to 1111, the results may be written to all word locations in the target register. One skilled in the art will recognize that the enablement logic may be reversed, wherein logic ‘0’ denotes an enabled bit and logic ‘1’ denotes a disabled bit.

One skilled in the art will further recognize that while a mask comprising four bits is described herein, embodiments of the invention are not limited as such. More generally, any number of mask bits may be used to specify any number of locations within the target register. For example, 8 mask bits may be used to identify 8 half word locations or 16 mask bits to specify 16 byte locations in a 128 bit register, and so on.

In some embodiments of the invention one or more mask bits may determine a mask value, wherein the mask value is associated with one or more locations in the target register. For example, in one embodiment, the target register may include four locations. The four target register locations may be identified by two mask bits. For example, mask ‘00’ may identify word location 0, mask ‘01’ may identify word locations 0 and 1, mask ‘10’ may identify word locations 0, 1 and 2, and mask ‘11’ may identify word locations 0, 1, 2, and 3. Therefore, the number of mask bits may be fewer than the number of target register locations.

Furthermore, the particular instruction configuration depicted in FIG. 11 is not limiting on the invention. The dot product instruction may include any number of fields of any length, each field being provided for a predefined purpose, for example, providing an extended op-code field. More generally, any instruction providing a mask field 1105 for identifying one or more locations of a target register falls within the scope of the invention.

FIG. 12 illustrates an exemplary instruction stream to construct a new vector A in a single register R_(A) by performing a plurality of dot product instructions utilizing write masks. As illustrated, a first dot product instruction 1201 may perform a dot product operation between a vector contained in register R10 and R20 and store the scalar result to a particular location in register R_(A). Mask 1210, may determine a location in register R_(A) to which the scalar result may be stored. For example, mask 1210 has its first bit enabled, which may correspond to the word 0 location of register R_(A). Therefore, the scalar result, for example, x_(a) may be stored to the word 0 location of register R_(A).

While mask 1210 is shown with a single bit enabled, one skilled in the art will recognize that multiple bits may be enabled to store the scalar results in multiple locations of register R_(A). For example a first operand and a second operand of vector A may have the same value determined by dot product instruction 1210. Therefore, mask 1210 may include two enabled bits specifying locations in register R_(A) for storing the scalar result to the desired locations representing the first operand and the second operand.

The mask bits may be sent directly to a vector unit during execution of the instruction. The mask bits may flow down the pipeline of the vector unit and may be used to create write enables when writing data back to the target register. For example, referring back to FIG. 7, the write enables may determine the data written back to the target register in the register file via path 721.

Similarly, dot product instruction 1202 may perform a dot product operation between vectors contained in registers R30 and R40, and the scalar result y_(a) may be stored in the word 1 location of register R_(A), and dot product instruction 1203 may perform a dot product operation between vectors contained in registers R50 and R60, and the scalar result z_(a), may be stored in the word 2 location of register R_(A). Therefore, the construction of vector A in register R_(A) may be accomplished without having to issue permute instructions and without the use of temporary registers to hold vector A operands, as was required in FIG. 10. Furthermore, instructions 1201-1203 are not dependent, thereby avoiding stalling of the pipeline between instructions.

FIG. 13 is a flow diagram of exemplary operations performed to construct a new vector by performing a plurality of dot product operations. The operations may begin in step 1301 by generating a plurality of dot product instructions for generating vector operands for the new vector. Each dot product instruction may perform a dot product operation between two vectors contained in one or more registers and generate a scalar result, wherein each scalar result may represent a vector operand for the new vector.

In step 1302, a write mask may be defined for each dot product instruction. The write mask may determine one or more locations in a target register in which a vector operand may be written. In step 1303, the dot product instructions may be executed by a vector unit to generate operands of the new vector and store the operands in desired locations within the target register.

CONCLUSION

By providing a dot product instruction which allows the specification of a particular location of a target register in which to move data, embodiments of the invention significantly reduce the number of instructions, dependencies between instructions, and the usage of temporary registers during vector processing, thereby improving performance.

While the foregoing is directed to embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof, and the scope thereof is determined by the claims that follow. 

1. A method for storing data in a target register, comprising: receiving a dot product instruction specifying at least one source register comprising vector operands for performing a dot product operation, the target register, and a write mask, wherein the write mask identifies one or more locations of the target register for writing data; and in response to receiving the dot product instruction, performing the dot product operation and storing a scalar result of the dot product operation to the one or more locations of the target register identified by the write mask.
 2. The method of claim 1, wherein the write mask comprises a plurality of bits, wherein the plurality of bits determine a value of the write mask, the value being associated with the one or more locations of the target register.
 3. The method of claim 2, wherein each of the plurality of bits is associated with a location in the target register.
 4. The method of claim 2, wherein identifying the one or more locations of the target register comprises enabling one or more of the plurality of bits associated with the one or more locations of the target register.
 5. The method of claim 4, wherein, enabling one or more of the plurality of bits associated with the one or more locations of the target register comprises setting the one or more bits to logic ‘1’.
 6. The method of claim 1, wherein the one or more locations of the target register are word locations.
 7. The method of claim 6, wherein each of the word locations comprise vector data.
 8. A method for constructing a vector in a target register, comprising: generating a plurality of dot product instructions, each dot product instruction specifying at least one source register comprising vector operands for performing a dot product operation, and the target register, wherein each dot product instruction generates a scalar result representing an operand of the vector; setting a mask field in each of the plurality of dot product instructions, wherein the mask field identifies one or more locations of the target register for storing the scalar result of the dot product operation; and executing the dot product instructions to store each operand of the vector at the one or more locations in the target register identified by the mask field to construct the vector in the target register.
 9. The method of claim 8, wherein the mask field comprises a plurality of bits, wherein the plurality of bits determine a value of the write mask, the value being associated with the one or more locations of the target register.
 10. The method of claim 9, wherein identifying the one or more locations of the target register comprises enabling one or more of the plurality of bits associated with the one or more locations of the target register.
 11. The method of claim 10, wherein, enabling one or more of the plurality of bits associated with the one or more locations of the target register comprises setting the one or more bits to logic ‘1’.
 12. The method of claim 8, wherein the one or more locations of the target register are word locations.
 13. The method of claim 12, wherein each of the word locations comprise vector data.
 14. A system, comprising a plurality of processors communicably coupled with one another, wherein each processor comprises: a register file comprising a plurality of registers; and at least one vector unit, wherein the vector unit is configured to: receive a dot product instruction specifying at least one source register comprising vector operands for performing a dot product operation, a target register, and a write mask, the write mask identifying one or more locations in the target register, and execute the dot product instruction by performing the dot product operation and storing a scalar result of the dot product operation to the one or more locations of the target register identified by the write mask.
 15. The system of claim 14, wherein the write mask comprises a plurality of bits, wherein the plurality of bits determine a value of the write mask, the value being associated with the one or more locations of the target register.
 16. The system of claim 15, wherein each of the plurality of bits is associated with a location in the target register.
 17. The system of claim 15, wherein one or more of the plurality of bits are enabled to identify the one or more locations of the target register.
 18. The system of claim 17, wherein to enable the one or more bits, the one or more bits are set to logic ‘1’.
 19. The system of claim 14, wherein the one or more locations of the target register are word locations.
 20. The system of claim 14, wherein each of the word locations comprise vector data. 